Release History > PTV xServer 1.18.1

Release Notes PTV xServer 1.18.1

PTV xCluster Server

1.18.1.2

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.
Bug Fix: The distanceCalculation parameter is nillable.

1.18.1.1

Bug Fix: Current and last row index of distance matrix calculation progress did not match the actual number of rows (it was 1 too large).

1.18.1.0

Feature: Replaced routing profiles called dimaCar.ini and dimaTruck.ini by files in the XML format. Users of previous versions must convert the profiles using the profile converter from /tools/profileconverter, a documentation is provided there. The new XML profiles can be found in /conf/profiles. Please note that the PTV xCluster Server does not support the modification of the profiles via request (snippet mechanism).
Feature: Introduced FeatureLayer as already available in PTV xRoute Server, a generic mechanism to consider additional data such as traffic patterns, preferred routes and so on (special license needed).
Feature: PTV xRoute, PTV xTour, PTV xCluster and PTV xDima Server use the same XML profiles for routing parametrisation. These profiles can now be interchanged between these four PTV xServer. Please note that the PTV xDima, PTV xCluster and PTV xTour Server ignore the profile elements GeoDataSource and BreakAndRestRules.
Improvement: Increased accuracy of the driving periods stored in distance matrices. So far driving periods are stored in 10s units, now up to 1s units is possible (depending on the size of the driving period).
Improvement: The number of locations per distance matrix is now limited to 40000 (only 64-bit version).
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.

PTV xDima Server

1.18.1.3

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.
Improvement: Export and import of large distance matrices( > 2 GB) is possible.

1.18.1.2

Bug Fix: Correct import and export of non-calculated matrix entries (e.g. in case of no route found).
Bug Fix: Hardware requirements and timeout for routing network generator adjusted.
Bug Fix: Fixed bug concerning treatment of turning ban costs in special cases while using high-performance routing networks.

1.18.1.1

Bug Fix: Current and last row index of distance matrix calculation progress did not match the actual number of rows (it was 1 too large).
Bug Fix: Fixed bug concerning treatment of turning ban costs in generation of high-performance routing data (routingnetworkgenerator).

1.18.1.0

Feature: Replaced routing profiles called dimaCar.ini and dimaTruck.ini by files in the XML format. Users of previous versions must convert the profiles using the profile converter from /tools/profileconverter, a documentation is provided there. The new XML profiles can be found in /conf/profiles. Please note that the PTV xDima Server does not support the modification of the profiles via request (snippet mechanism).
Feature: Introduced FeatureLayer as already available in PTV xRoute Server, a generic mechanism to consider additional data such as traffic patterns, preferred routes and so on (special license needed).
Feature: PTV xRoute, PTV xTour, PTV xCluster and PTV xDima Server use the same XML profiles for routing parametrisation. These profiles can now be interchanged between these four PTV xServer. Please note that the PTV xDima, PTV xCluster and PTV xTour Server ignore the profile elements GeoDataSource and BreakAndRestRules.
Improvement: Increased accuracy of the driving periods stored in distance matrices. So far driving periods are stored in 10s units, now up to 1s units is possible (depending on the size of the driving period).
Improvement: The number of locations per distance matrix is no longer limited to 18918 (only 64-bit version).
Improvement: Faster loading times of high-performance routing networks via caching mechanisms.
Improvement: The method exportDima() now writes the routing profile. This routing profile can then be used for the import of distance matrices.
Improvement: Due to improved locking mechanisms the method unlockDima() is no longer necessary. It is marked as deprecated and performs no operation.
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.
Bug Fix: In case of calculating the distance matrices with high-performance routing networks, only the routing profile of the high-performance routing network is used.

Caution: The binary format of the distance matrix and the high-performance routing network has changed. Please recalculate all distance matrices and high-performance routing networks.

PTV xLocate Server

1.18.1.4

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.
Bug Fix: Address search returns correct co-ordinates even when the map data is incomplete.

1.18.1.3

Bug Fix: The provider segment ID is returned correctly also in case a node resides on a tile edge.

1.18.1.2

Feature: For all geocoding and reverse geocoding use cases the new additional field "province" contains the admin entity below "state", such as "Kreis" in Germany, "provincia" in Italy, "département" in France, "oblast" in Russia. This feature is currently available only for HERE maps.
Improvement: Added support for additional country codes (PTV codes 982-987). Updated ISO2 and codeplate for Kosovo (381).

1.18.1.1

Bug Fix: The management console configurator now lists the xml-based nativeEngineProfile and nativeReverseEngineProfile files.

1.18.1.0

Feature: New reverse geocoding parameters ENGINE_MINSIZE and ENGINE_RETURNALLEQUALDISTANCES.
Improvement: Support of EPSG codes in the coordinate format of the CallerContext (e.g. EPSG:4326 corresponds to WGS 84).
Improvement: The number of significant figures for response geometries is configurable (see entry responseGeometrySignificantFigures in xserver.property with default 11).
Improvement: The maximum number of results returned is now limited to 1000.
Improvement: Like the multi-field search the single-field search now queries not only the street directory of each found city, but also connected street directories (present when a street from one city is listed in the street directory of another, typically an adjacent city).
Improvement: Suggestion search delivers post code and town in the same order as typed in.
Improvement: Suggestion search delivers also house numbers.
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.
Bug Fix: The special character table was corrected for Scandinavian languages.

PTV xMap Server

1.18.1.4

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.

1.18.1.3

Bug Fix: In Australia and North America the rendering of truck attributes is working as intended.

1.18.1.2

Bug Fix: The default value for MapParams.referenceTime is localTime.NOW instead of 1.1.1970, similar to xRoute.
Bug Fix: Rendering bug fixed by using Leaflet with FeatureLayer.
Bug Fix: FeatureLayer traffic patterns are now displayed together with preferred routes on lower zoom levels (smaller than 4).
Bug Fix: Fixed startup problems with FeatureLayer.

1.18.1.1

Improvement: Better performance for rendering FeatureLayer.
Bug Fix: Fixed various bugs regarding rendering of FeatureLayer, especially when zooming in or out.

1.18.1.0

Feature: Introduced FeatureLayer, a generic mechanism to render additional data such as traffic patterns, preferred routes and so on (special license needed). The configuration of the FeatureLayer rendering is possible via an XML profile.
Feature: New alternative rendering profile silkysand.
Improvement: Support of EPSG codes in the coordinate format of the CallerContext (e.g. EPSG:4326 corresponds to WGS 84).
Improvement: The number of significant figures for response geometries is configurable (see entry responseGeometrySignificantFigures in xserver.property with default 11).
Improvement: The internal default setting for maximal resolution is changed from 0.004 to 0.04 SmartUnit/pixel.
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.
Bug Fix: Improved image quantisation in order to ensure stable background colours.
Bug Fix: Crash fixed when loading an invalid image in JPEG format.

PTV xMapmatch Server

1.18.1.3

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.
Bug Fix: The provider segment ID is returned correctly also in case a node resides on a tile edge.

1.18.1.2

Improvement: Optimised speed limit access performance.
Bug Fix: Does no longer accidentally report speed limits depending on weather conditions.
Bug Fix: Fixed crash on speed limit access in special conditions.
Bug Fix: No longer logs wrong errors concerning certain map transitions.

1.18.1.1

Bug Fix: Property based profiles are no longer taken into account. FailOnIllegalProfile of xserver.properties also works for xml profiles.
Bug Fix: Completed effective profile, movingDistanceRangeMaximum and movingDistanceRangeMinimum were always 0.

1.18.1.0

Feature: Replaced profiles called xmapmatch-<profile>.properties by files in the XML format. Users of previous versions must convert the profiles using the profile converter from /tools/profileconverter, a documentation is provided there. The new XML profiles can be found in /conf/profiles.
Feature: New interface method matchPositions() with a more flexible possibility to configure the returned result.
Improvement: Support of EPSG codes in the coordinate format of the CallerContext (e.g. EPSG:4326 corresponds to WGS 84).
Improvement: The number of significant figures for response geometries is configurable (see entry responseGeometrySignificantFigures in xserver.property with default 11).
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.

PTV xRoute Server

1.18.1.6

Bug Fix: Fixed performance problem in routing algorithm in case of certain bonus values (-99) in the router profile.

1.18.1.4

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.

1.18.1.3

Bug Fix: Fixed bug concerning RE weight violation description not showing the weight in [kg].
Bug Fix: Breaks and rests are now calculated as intended when driver settings are specified.

1.18.1.2

Bug Fix: Fixed performance problem in case of using costsPercentageToPassOn for ecotaxe calculations.
Bug Fix: Fixed start up problems with shared-memory files blocked by the operating system.
Bug Fix: Fixed start up problems when creating a temporary folder if poolSize is greater than 1.

1.18.1.1

Bug Fix: Fixed crash on illegal combinedTransportID.
Bug Fix: Fixed bug in matrix calculation when the request contains a location (waypoint) consisting of multiple points and the link type is "SMART".

1.18.1.0

Feature: New FeatureLayer truck restrictions zones is possible to consider in routing from this version on.
Feature: PTV xRoute, PTV xTour, PTV xCluster and PTV xDima Server use the same XML profiles for routing parametrisation. These profiles can now be interchanged between these four PTV xServer.
Feature: Time zone offsets can be requested for stations and segments.
Improvement: Support of EPSG codes in the coordinate format of the CallerContext (e.g. EPSG:4326 corresponds to WGS 84).
Improvement: The number of significant figures for response geometries is configurable (see entry responseGeometrySignificantFigures in xserver.property with default 11).
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.
Bug Fix: Vehicle classification of trucks and vans (based on total weight) was harmonised.
Bug Fix: The trailer weight given in the vehicle is now added to the total actual weight of the vehicle. That resulting total weight is used to evaluate whether a segment is forbidden due to truck attributes.
Bug Fix: Fixed bug reading speed limits (for some segments wrong extra speed limits have been returned).
Bug Fix: Countries to avoid are evaluated correctly.

PTV xTour Server

1.18.1.3

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.

1.18.1.2

Bug Fix: If a vehicle in the fleet list is null, a required parameter exception is now thrown.
Bug Fix: Hardware requirements and timeout for routing network generator adjusted.
Bug Fix: Fixed bug concerning treatment of turning ban costs in special cases while using high-performance routing networks.

1.18.1.1

Bug Fix: As the input plan must contain at least one tour point and as planBasicTours throws an exception on missing tour points, planSequence now also throws an exception in that case instead of ignoring all other attributes.
Bug Fix: Current and last row index of distance matrix calculation progress did not match the actual number of rows (it was 1 too large).
Bug Fix: Fixed bug concerning treatment of turning ban costs in generation of high-performance routing data (routingnetworkgenerator).

1.18.1.0

Feature: Replaced routing profiles called dima<profile>.ini by files in the XML format. Users of previous versions must convert the profiles using the profile converter from /tools/profileconverter, a documentation is provided there. The new XML profiles can be found in /conf/profiles.
Feature: Introduced FeatureLayer as already available in PTV xRoute Server, a generic mechanism to consider additional data such as traffic patterns, preferred routes and so on (special license needed).
Feature: PTV xRoute, PTV xTour, PTV xCluster and PTV xDima Server use the same XML profiles for routing parametrisation. These profiles can now be interchanged between these four PTV xServer. Please note that the PTV xDima, PTV xCluster and PTV xTour Server ignore the profile elements GeoDataSource and BreakAndRestRules.
Feature: PTV xTour is now available for Linux x64.
Improvement: Increased accuracy of the driving periods stored in distance matrices. So far driving periods are stored in 10s units, now up to 1s units is possible (depending on the size of the driving period).
Improvement: The number of locations per distance matrix is now limited to 40000 (only 64-bit version).
Improvement: Faster loading times of high-performance routing networks via caching mechanisms.
Improvement: Support of EPSG codes in the coordinate format of the CallerContext (e.g. EPSG:4326 corresponds to WGS 84).
Improvement: Complete restructure of the PTV xServer documentation and summary in one manual.
Improvement: Revised viewer of the PTV xServer configuration files in the management console.
Bug Fix: In case of calculating the distance matrices with high-performance routing networks, only the routing profile of the high-performance routing network is used.
Bug Fix: Tour events are consistent with times at tour points.
Bug Fix: Analyse and proposal methods ignore all trucks and their tours when at least one tour in the truck's chain is violated (equivalent to the automatic planning).

Caution: The binary format of the distance matrix and the high-performance routing network has changed. Please recalculate all distance matrices and high-performance routing networks.

PTV xServer bundle

1.18.1.3

Improvement: Updated Java server runtime to JDK 1.7.0_71. Java clients are still compliant with Java 6.
Includes: PTV xCluster Server 1.18.1.2
Includes: PTV xDima Server 1.18.1.3
Includes: PTV xLocate Server 1.18.1.4
Includes: PTV xMap Server 1.18.1.4
Includes: PTV xMapmatch 1.18.1.3
Includes: PTV xRoute Server 1.18.1.4
Includes: PTV xTour Server 1.18.1.3 (Linux 32bit not available)
Includes: PTV xServer add-on AJAX Maps 3.0.4.0
Includes: Code Sample Browser 1.18.1.0

1.18.1.2

Includes: PTV xCluster Server 1.18.1.1
Includes: PTV xDima Server 1.18.1.2
Includes: PTV xLocate Server 1.18.1.2
Includes: PTV xMap Server 1.18.1.2
Includes: PTV xMapmatch 1.18.1.2
Includes: PTV xRoute Server 1.18.1.2
Includes: PTV xTour Server 1.18.1.2 (Linux 32bit not available)
Includes: PTV xServer add-on AJAX Maps 3.0.4.0
Includes: Code Sample Browser 1.18.1.0

1.18.1.1

Includes: PTV xCluster Server 1.18.1.1
Includes: PTV xDima Server 1.18.1.1
Includes: PTV xLocate Server 1.18.1.1
Includes: PTV xMap Server 1.18.1.1
Includes: PTV xMapmatch 1.18.1.1
Includes: PTV xRoute Server 1.18.1.1
Includes: PTV xTour Server 1.18.1.1 (Linux 32bit not available)
Includes: PTV xServer add-on AJAX Maps 3.0.4.0
Includes: Code Sample Browser 1.18.1.0